fix(facts): use vertical m for submarine rangefinder distance facts#14620
fix(facts): use vertical m for submarine rangefinder distance facts#14620Bartok9 wants to merge 4 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #14620 +/- ##
==========================================
+ Coverage 25.47% 31.58% +6.11%
==========================================
Files 769 785 +16
Lines 65912 66985 +1073
Branches 30495 31029 +534
==========================================
+ Hits 16788 21159 +4371
+ Misses 37285 31443 -5842
- Partials 11839 14383 +2544
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Build ResultsPlatform Status
All builds passed. Pre-commit
Pre-commit hooks: 0 passed, 0 failed, 0 skipped. Test Resultslinux-coverage-integration: 33 passed, 0 skipped Code CoverageCoverage: 67.8% No baseline available for comparison Artifact Sizes
Updated: 2026-07-19 13:14:54 UTC • Commit: c7c7473 • Triggered by: Android |
82bb408 to
8f52999
Compare
Rangefinder range and target are vertical-axis lengths for ROV displays. Plain "m" skips Vertical Distance unit preference conversion.
8f52999 to
e5537a4
Compare
Summary
rangefinderDistanceandrangefinderTargetunits tovertical m.Motivation
ROV rangefinder range/target are vertical-axis lengths. Plain
mskips Vertical Distance unit conversion.Verification
Notes
AI-assisted; human-reviewed. Complements prior vertical-m fact work (DonLakeFlyer coalesce credited earlier merges).